UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

tc Server CaSa must produce log records that contain sufficient information to establish the outcome (success or failure) of events.


Overview

Finding ID Version Rule ID IA Controls Severity
V-88865 VROM-TC-000235 SV-99515r1_rule Medium
Description
After a security incident has occurred, investigators will often review log files to determine what happened. tc Server HORIZON must create a log entry when a user accesses the system and the system authenticates users. The logs must contain information about user sessions to include what type of event occurred, when (date and time) events occurred, where within the server the events occurred, the client source of the events, the outcome (success or failure) of the event, the identity of the user/subject/process associated with the event. Like all web servers, tc Server generates HTTP status codes. The status code is a three-digit indicator of the outcome of the server's response to the request.
STIG Date
VMware vRealize Operations Manager 6.x tc Server Security Technical Implementation Guide 2018-10-12

Details

Check Text ( C-88557r1_chk )
At the command prompt, execute the following command:

tail /storage/log/vcops/log/casa/localhost_access_log.YYYY-MM-dd.txt

Note: Substitute the actual date in the file name.

If the HTTP status codes are not being recorded, this is a finding.

Note: HTTP status codes are 3-digit codes, which are recorded immediately after "HTTP/1.1"
Fix Text (F-95607r1_fix)
Navigate to and open /usr/lib/vmware-casa/casa-webapp/conf/server.xml.

Navigate to and locate .

Configure the node with the below.

Note: The “AccessLogValve” should be configured as follows:

directory="logs"
pattern="%h %l %u %t "%r" %s %b"
prefix="localhost_access_log."
suffix=".txt"/>